Release 10.1A: OpenEdge Development:
Messaging and ESB

OpenEdge Adapter for Sonic ESB

The OpenEdge Adapter for Sonic ESB provides the 4GL-SOAP API that enables AppServer applications to receive and respond to requests over the enterprise service bus. It is functionally equivalent to the OpenEdge Web Services Adapter (WSA), which enables the exposure of AppServer applications as Web services by performing the same conversions between the 4GL and SOAP protocols. The two adapters differ only with respect to their hosting environments and, as a result, the tools that you use to manage and configure them. For information on the OpenEdge Adapter for Sonic ESB architecture, see OpenEdge Getting Started: Application and Integration Services .

OpenEdge Adapter for Sonic ESB configuration and management

The OpenEdge Adapter for Sonic ESB is installed as an option through the OpenEdge installation program. Installation registers the OpenEdge service type definition as an available application type in the Sonic ESB environment. It also installs a custom resource editor, which is used to set custom run-time properties and generate Web Services Description Language (WSDL) files for OpenEdge services.

Following completion of development and testing of an AppServer application designed for use as a service, the OpenEdge Proxy Generator tool is used to generate a service definition in the form of a Web Service Mapping (WSM) file. Alternatively, for an existing Web service, the OpenEdge Web Services Adapter can export a Web Service Definition (WSD) file. A WSD file is similar to a WSM file, but it includes any custom run-time properties previously defined for the service.

Once the WSM or WSD file is available, all configuration and management operations take place within the Sonic environment. The appropriate person uses the tools in the Sonic ESB Explorer to:

Edit the run-time properties specified in the WSM or WSD file, if necessary.
Generate a WSDL file, if desired.
Process the WSM or WSD service definition file and create an instance of the OpenEdge service type.
Deploy the service in a Sonic ESB container, thereby making it available for use.

OpenEdge Adapter for Sonic ESB operation

Once deployed in a container, an OpenEdge service functions like any other Sonic ESB service. Any client application that conforms to the requirements specified by the WSDL file can send requests and receive responses through the standard Sonic ESB facilities. The service can be included in a process definition, or it can function as a standard Web service.